Use golang-based tool for AWS instances availability#17953
Use golang-based tool for AWS instances availability#17953ameukam wants to merge 1 commit intokubernetes:masterfrom
Conversation
Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
size/L
|
cc @justinsb |
|
/retest |
|
@ameukam: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| @@ -0,0 +1,24 @@ | |||
| module k8s.io/kops/tests/e2e/scenarios/ai-conformance/tools/check-aws-availability | |||
There was a problem hiding this comment.
Is there another go.mod needed? We should already have these modules in the main go.mod.
There was a problem hiding this comment.
wanted to go simple and fast. we can iterate on package organization and integration in follow-up PRs.
|
Why do we need this? we can pick specific regions that have plenty of GPU enabled instances |
It's not clear from the AWS API if a GPU-based instance is always guaranteed everytime a test is triggered. And not every region has all the GPU-enabled instances. |
|
We have the same issue with GCP and use an older generation that has plenty of availability. |
4 participants
Help avoid the dependency to AWS CLI